Analysis of Strava activities - OSM explains hikes' stops

In this notebook is presented an analysis of an hike and how it's possible to reconstruct its routes, trajectories and stops. And, more interestingly, the motivations behind those stops.

Data loading

This part is common for all notebooks, for simplicity. It takes all the Strava activities collected and stores them in lists, dataframes, geodataframes and trajectories for every type of activity (runs, hikes, rides and all).

Vigolana hike analysis

Hiking activities could be interesting to analyze. For example, given that I'm not a good biker (or a good trail runner...yet), activities with an high elevation difference between highest and lowest points should be hikes.

Stops analysis

For example, activity n°115 has been a hike to the Vigolana Shelter (Madonnina) made last summer. Did I took any stop on my way up? Was them for any specific reason?

Let's see where these stops have been taken along the hike.

A possible cause for the stops could be the high elevation gain made in a short time. Let's check if it's the case.

In some cases stops could explained by elevation gain in a short amount of time, but in other there should be different reasons. A good viewpoint to take pictures while resting, maybe? Let's check with the longest stop I took.

Including OSM data for the analysis

Apparently, I stopped for a short break, but also to take a nice picture and enjoy the view. Let's confirm it in the map seen before, but changing the layer with a more appropriate one.

As expected, with the OSM layer we can see that the longest stop has been taken in proximity (within 10m) of the viewpoint Polsa.
Fun fact: this viewpoint has been mapped last time in 2020 by the user Martin Larcher (https://www.openstreetmap.org/node/910787221); at the end of the hike we just analyzed, I spent the night in the Madonnina shelter with...Martin Larcher himself, along with his family!